Apparatus and methods for cell identification in wireless networks

ABSTRACT

Apparatus and methods for physical cell identification within one or more wireless networks. In one embodiment, conflicts in PCI values which may exist within two or more mobile networks (e.g., PLMNs) of respective different operators when unlicensed spectrum is utilized (e.g., according to 3GPP 5G NR-U technology) are resolved. In one implementation, this functionality is provided by specifying one or more mobility-related parameters associated with various UE, such that serving gNBs can determine whether a given UE requires a mobility context, and as such whether it should conduct subsequent RF measurement reporting to report back potential conflicts in PCI it may encounter to the gNB. In one variant, the measurement reporting is configured to comply with 5G NR-U required “listen-before-talk” or LBT protocols; i.e., to measure parameters consistent with the LBT protocols to detect any such PCI-based conflicts.

PRIORITY

This application claims priority to U.S. Provisional Patent ApplicationSer. Nos. 62/745,065 and 62/752,002 filed Oct. 12, 2018 and Oct. 29,2018, respectively, each entitled “APPARATUS AND METHODS FOR CELLIDENTIFICATION IN WIRELESS NETWORKS,” each incorporated herein byreference in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND Technological Field

The present disclosure relates generally to the field of wirelessdevices and networks thereof, and specifically in one exemplary aspectto identification of one or more cells within one or more RANs (RadioArea Networks) of a radio network utilizing licensed and/or unlicensedspectrum.

Description of Related Technology

A multitude of wireless networking technologies, also known as RadioAccess Technologies (“RATs”), provide the underlying means of connectionfor radio-based communication networks to user devices. Such RATs oftenutilize licensed radio frequency spectrum (i.e., that allocated by theFCC per the Table of Frequency Allocations as codified at Section 2.106of the Commission's Rules). Currently only frequency bands between 9 kHzand 275 GHz have been allocated (i.e., designated for use by one or moreterrestrial or space radio communication services or the radio astronomyservice under specified conditions). For example, a typical cellularservice provider might utilize spectrum for so-called “3G” (thirdgeneration) and “4G” (fourth generation) wireless communications asshown in Table 1 below:

TABLE 1 Technology Bands 3G 850 MHz Cellular, Band 5 (GSM/GPRS/EDGE).1900 MHz PCS, Band 2 (GSM/GPRS/EDGE). 850 MHz Cellular, Band 5(UMTS/HSPA+ up to 21 1900 MHz PCS, Band 2 (UMTS/HSPA+ up to 21 4G 700MHz Lower B/C, Band 12/17 (LTE). 850 MHz Cellular, Band 5 (LTE).1700/2100 MHz AWS, Band 4 (LTE). 1900 MHz PCS, Band 2 (LTE). 2300 MHzWCS, Band 30 (LTE).

Alternatively, unlicensed spectrum may be utilized, such as that withinthe so-called ISM-bands. The ISM bands are defined by the ITU RadioRegulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of theRadio Regulations. In the United States, uses of the ISM bands aregoverned by Part 18 of the Federal Communications Commission (FCC)rules, while Part 15 contains the rules for unlicensed communicationdevices, even those that share ISM frequencies. Table 2 below showstypical ISM frequency allocations:

TABLE 2 Frequency Center range Type frequency Availability Licensedusers 6.765 MHz-6.795 MHz A  6.78 MHz Subject to local Fixed service &mobile acceptance service 13.553 MHz-13.567 MHz B  13.56 MHz WorldwideFixed & mobile services except aeronautical mobile (R) service 26.957MHz-27.283 MHz B  27.12 MHz Worldwide Fixed & mobile service exceptaeronautical mobile service, CB ratio 40.66 MHz-40.7 MHz  B  40.68 MHzWorldwide Fixed, mobile service & earth exploration-satellite service433.05 MHz-434.79 MHz A 433.92 MHz only in Region amateur service & 1,subject to radiolocation service, local acceptance additional apply theprovisions of footnote 5.280 902 MHz-928 MHz B   915 MHz Region 2 onlyFixed, mobile except (with some aeronautical mobile & exceptions)radiolocation service; in Region 2 additional amateur service 2.4GHz-2.5 GHz B  2.45 GHz Worldwide Fixed, mobile, radiolocation, amateur& amateur-satellite service 5.725 GHz-5.875 GHz B   5.8 GHz WorldwideFixed-satellite, radiolocation, mobile, amateur & amateur-satelliteservice   24 GHz-24.25 GHz B 24.125 GHz Worldwide Amateur,amateur-satellite, radiolocation & earth exploration-satellite service(active)   61 GHz-61.5 GHz A  61.25 GHz Subject to local Fixed,inter-satellite, mobile acceptance & radiolocation service 122 GHz-123GHz A  122.5 GHz Subject to local Earth exploration-satellite acceptance(passive), fixed, inter- satellite, mobile, space research (passive) &amateur service 244 GHz-246 GHz A   245 GHz Subject to localRadiolocation, radio acceptance astronomy, amateur & amateur-satelliteservice

ISM bands are also been shared with (non-ISM) license-freecommunications applications such as wireless sensor networks in the 915MHz and 2.450 GHz bands, as well as wireless LANs (e.g., Wi-Fi) andcordless phones in the 915 MHz, 2.450 GHz, and 5.800 GHz bands.

Additionally, the 5 GHz band has been allocated for use by, e.g., WLANequipment, as shown in Table 3:

TABLE 3 Dynamic Freq. Selection Band Name Frequency Band Required (DFS)?UNII-1  5.15 to 5.25 GHz No UNII-2  5.25 to 5.35 GHz Yes UNII-2 Extended 5.47 to 5.725 GHz Yes UNII-3 5.725 to 5.825 GHz No

User client devices (e.g., smartphone, tablet, phablet, laptop,smartwatch, or other wireless-enabled devices, mobile or otherwise)generally support multiple RATs that enable the devices to connect toone another, or to networks (e.g., the Internet, intranets, orextranets), often including RATs associated with both licensed andunlicensed spectrum. In particular, wireless access to other networks byclient devices is made possible by wireless technologies that utilizenetworked hardware, such as a wireless access point (“WAP” or “AP”),small cells, femtocells, or cellular towers, serviced by a backend orbackhaul portion of service provider network (e.g., a cable network). Auser may generally access the network at a node or “hotspot,” a physicallocation at which the user may obtain access by connecting to modems,routers, APs, etc. that are within wireless range.

5G New Radio (NR) and NG-RAN (Next Generation Radio Area Network)

NG-RAN or “NextGen RAN (Radio Area Network)” is part of the 3GPP “5G”next generation radio system. 3GPP is currently specifying Release 15NG-RAN, its components, and interactions among the involved nodesincluding so-called “gNBs” (next generation Node B's or eNBs). NG-RANwill provide high-bandwidth, low-latency wireless communication andefficiently utilize, depending on application, both licensed andunlicensed spectrum of the type described supra in a wide variety ofdeployment scenarios, including indoor “spot” use, urban “macro” (largecell) coverage, rural coverage, use in vehicles, and “smart” grids andstructures. NG-RAN will also integrate with 4G/4.5G systems andinfrastructure, and moreover new LTE entities are used (e.g., an“evolved” LTE eNB or “eLTE eNB” which supports connectivity to both theEPC (Evolved Packet Core) and the NR “NGC” (Next Generation Core).

The NG-RAN (5G) System architecture is designed to support dataconnectivity and services offering with higher throughput and lowerlatency. FIG. 1 shows the 5G architecture 100 as defined in 3GPP TS23.501 (FIG. 4.2.3-1 thereof).

An existing 3GPP LTE/LTE-A/EPC (i.e., 4G or 4.5G system) cannot beupdated to support 5G; hence, 3GPP has also defined interworkingprocedures between such 4G/4.5G and 5G systems. FIG. 2a shows thearchitecture 200 for interworking between 5GS and EPC/E-UTRAN as definedin TS 23.501 (FIG. 4.3.1-1 thereof), specifically the non-roamingarchitecture for interworking between the 5GS and the EPC/E-UTRAN. Twodifferent RAN technologies are supported; i.e., E-UTRAN (4G/4.5G) 202,and 5G (NG-RAN) 204. FIG. 2b shows a roaming architecture counterpart(i.e., with HPLMN and visited network (VPLMN).

In LTE and 5G NR, for a given cell, the cognizant eNB/gNB broadcasts aPhysical Cell ID (PCI). The Physical Cell ID is the identification of acell at the physical layer (PHY). Under LTE (pre Release 15), up to 504unique PCIs can be specified. 5G NR (Release 15 and beyond) presentlyallows up to 1008 unique PCIs.

However, a given PLMN (e.g., HPLMN or VPLMN, such as those describedabove with respect to FIGS. 1-2 b) has many cells. But since the PCIsare rather limited in number, the notion of an ECGI (E-UTRAN Cell GlobalIdentifier; LTE), and NCGI (NR Cell Global Identifier; 5G NR) wasintroduced, wherein a PLMN-ID is used in addition to the PCI to uniquelyidentify a given cell within a given PLMN (and also across it; i.e.,inter-PLMN). The ECGI is constructed from the MCC (Mobile Country Code),MNC (Mobile Network Code) and the ECI (E-UTRAN Cell Identifier), whilethe NCGI is constructed from the PLMN identity to which the cell belongsand the NR Cell Identity (NCI) of the cell.

Typically, the UE 222 performs Measurement Reporting, under networkdirective, based on detected PCIs for a given EARFCN (E-UTRA AbsoluteRadio Frequency Channel Number) or frequency/set of frequencies. Theremay exist scenarios where in a given geographic area, two or more PLMNsbroadcast the same PCI as seen by a UE. This situation leads to what isreferred to as “PCI Confusion;” i.e., an ambiguity as to which PLMN agiven PCI detected by a UE belongs.

Automatic Neighbor cell Relations (ANR) (see e.g., 3GPP TS 36.300) wasdeveloped to solve the foregoing issue. In ANR, an eNB/gNB—uponreceiving Measurement Reports containing the PCI from the UE—instructsthe RRC_CONNECTED mode UE to read all broadcast ECGI(s)/NCGI(s), TAC(s),RANAC(s), PLMN ID(s) and LTE/NR frequency band(s) of the cell identifiedvia the reported PCI. Using this information, the eNB/gNB formulates aneighbor cell relationship, and can use this information to update the“whitelist” or “blacklist” and forward to the UE 222. Using this updatedinformation, the UE can adjust its future Measurement Reports. Thisupdate information can also be used across PLMN operators to coordinatePCIs of cells, so that the aforementioned ambiguity or confusion isavoided (i.e., two PLMNs with common coverage where a UE might belocated will not utilize the same PCI).

3GPP TS 23.501 and TS 23.502 also support a mode known as MICO (MobileInitiated Connection Only) which allows the network to controlRegistration Areas, Paging and other related features for certaindevices which are expected to operate only in MO-only mode. However,MICO mode was designed for UEs which mostly have UL-heavy transmissions;e.g., IoT sensors. Although such devices could be limited in terms ofmobility, it is not a strict requirement, and there is no mechanismdetermination of mobility (or lack thereof).

The Unlicensed Problem

As of the date of this disclosure, design of NR for Unlicensed spectrum(NR-U) is underway in 3GPP for Releases 15 and 16. NR-U is being definedfor three (3) use-cases: (i) Carrier Aggregation (CA), (ii) DualConnectivity (DC), and (iii) Standalone (SA). (Licensed) NR's design isused as the baseline for NR-U and as such, every NR-U cell willbroadcast a PCI, as well as every licensed cell. Unlike licensedspectrum where a single operator owns a frequency range, unlicensedspectrum is open to all for use.

Accordingly, as shown in FIG. 2c , many different network operators(e.g., PLMN providers) could use same PCI at a given frequency withinboth the licensed and the unlicensed spectrum to identify theirrespective cells (i.e., PCI_(L) and PCI_(U), respectively as shown inFIG. 2c ). Given the nature of spectrum, coordination among such PLMNproviders cannot be assumed, and in fact given the ad hoc nature ofunlicensed spectrum, it is likely that coordination will not exist.

Moreover, the foregoing issue is exacerbated due to the NR-Urequirements to: a) perform LBT (Listen Before Talk) protocols to gainaccess to physical medium for transmission; see, e.g., 3GPP TS 38.889(or TS 37.213 for LTE-LAA), and/or b) account for transmission failures,and implement resulting exponential back-off mechanisms.

Based on the foregoing, no viable mechanism for cell identifier/identitymanagement within unlicensed environments (including for instance the 5GNR-U environment) currently exists.

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for providing optimized identification ofcells, such as for example those supported by a 5G NR-U enabled gNB orits broader PLMN.

In a first aspect of the disclosure, a method for cell identificationwithin a wireless network is described. In one embodiment, the methodincludes: identifying a set of candidate user devices (e.g., UE(s)) forwhich to apply the cell identifier resolution mechanism; instructing theidentified set of user devices to perform a measurement protocol; andbased on the results of the measurement protocol, configure at least onelisting of cell identifiers.

In another embodiment, the method includes using at least one gNB toidentify a set of candidate UE(s) for which to apply PCI confusionresolution mechanism; instructing, via the at least one gNB, theidentified set of UEs to perform Measurement Reports taking LBT intoaccount; and using Measurement Reports provided by UE to update thewhite/black lists to include/exclude unrelated PCIs.

In an additional aspect of the disclosure, computer readable apparatusis described. In one embodiment, the apparatus includes a storage mediumconfigured to store one or more computer programs, and includes aprogram memory or HDD or SSD on a computerized device such as a CU of a5G NR gNB. In one variant, the one or more computer programs areconfigured to evaluate whether a conflict between two PLMNs (e.g., a 5GNR licensed PLMN and a 5G NR-U unlicensed PLMN) exists, and invoke oneor more resolution mechanisms as required.

In a further aspect, a wireless access node is disclosed. In oneembodiment, the node comprises a computer program operative to executeon a digital processor apparatus, and configured to, when executed,obtain data from a control or network entity with which the node isassociated, and based on the data, cause selective implementation ofconflict resolution protocols within the population of user devicesserved by the access node.

In another embodiment, the node comprises a 3GPP-compliant gNB or eNB.

In another aspect of the disclosure, a method for identifying a subsetof user devices (e.g., UEs) is disclosed. In one embodiment, the methodincludes inserting parametric data relating to a use scenario or contextinto a protocol message delivered to a base station or RAN (e.g., 5GgNB). The parametric data is extracted by the gNB and used to determinewhether subsequent operations, such as Measurement Reporting, should beperformed for each UE based thereon.

In another embodiment, a UE provides data (e.g., a “noMobilityRequired”parameter or field) to indicate that no mobility is required, via theUE-NR-Capability IE which is included in UECapabilityInformation message(the latter sent in response to UECapabilityInquiry message). Uponreception of the provided data, the cognizant gNB can determine whetherthe UE can support the PCI conflict resolution mechanism or not andhence when combined information received e.g., from the AMF (e.g., overN2-AP INITIAL CONTEXT SETUP REQUEST), the gNB can accurately decidewhether or not and how to apply PCI conflict resolution mechanism forthe UE.

In another aspect of the disclosure, a mobile computerized device isdisclosed. In one embodiment, the device includes a 3GPP-compliant UE(user equipment) which is configured.

In an additional aspect of the disclosure, computer readable apparatusis described. In one embodiment, the apparatus includes a storage mediumconfigured to store one or more computer programs, and includes aprogram memory or HDD or SSD on a computerized device such as a 5G NRgNB or AMF.

In yet another aspect, a system is disclosed. In one embodiment, thesystem includes (i) an HSS+UDM entity with NMR database, and (ii) one ormore PCRE-enabled RAN or AMF entities which cooperate with the HSS+UDMentity to enable PCI conflict resolution in, inter alia, unlicensed 5Gspectrum usage scenarios.

In another aspect of the disclosure, a method for limiting a scope of aPCI search is disclosed. In one embodiment, the method includesdetermining a number to which to limit the search by one or more UE(s),and transmitting an IE from a base station (e.g., gNB) to the one ormore UE(s) to restrict the subsequent search and reporting by the UE tothe specified number.

In a further aspect, a method of conducting Physical Cell ID (PCI)conflict resolution is disclosed. In one embodiment, the method includesobtaining one or more Public Land Mobile Network ID (PLMN ID) values viaa PLMN-ID value within a measurement results reporting informationelement (IE).

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram of a prior art 5G systemarchitecture and the various components thereof.

FIG. 2a is a block diagram showing the extant architecture forinterworking between 5GS and EPC/E-UTRAN as defined in 3GPP TS 23.501(FIG. 4.3.1-1 thereof), specifically the non-roaming architecture forinterworking between the 5GS and the EPC/E-UTRAN.

FIG. 2b shows a prior art roaming architecture counterpart to thearchitecture of FIG. 2a (i.e., with HPLMN and visited network (VPLMN)).

FIG. 2c shows a graphical representation of the PCI “confusion” problembetween licensed and unlicensed spectrum networks within the exemplary5G NR context.

FIG. 3 is a logical flow diagram illustrating one embodiment of ageneralized method of PCI conflict resolution according to the presentdisclosure.

FIG. 3a is a logical flow diagram illustrating one embodiment of userdevice set identification within the generalized method of FIG. 3.

FIG. 3b is a logical flow diagram illustrating one embodiment of userdevice measurement reporting within the generalized method of FIG. 3.

FIG. 3c is a logical flow diagram illustrating a second embodiment ofuser device measurement reporting within the generalized method of FIG.3.

FIG. 3d is a logical flow diagram illustrating one embodiment ofwhitelist/blacklist updating based on measurement reporting, within thegeneralized method of FIG. 3.

FIG. 4 is a functional block diagram of a first exemplary embodiment ofan enhanced 5G NR network architecture according to the presentdisclosure.

FIG. 4a is a functional block diagram of a first exemplaryimplementation of the architecture of FIG. 4 within a non-roamingE-UTRAN/5G network architecture according to the present disclosure.

FIG. 4b is a functional block diagram of a second exemplaryimplementation of the architecture of FIG. 4 within a non-roamingE-UTRAN/5G network architecture according to the present disclosure.

FIG. 4c is a functional block diagram of a first exemplaryimplementation of the architecture of FIG. 4 within a roaming E-UTRAN/5Gnetwork architecture according to the present disclosure.

FIG. 5a is a functional block diagram of a first exemplary MSO/MNOnetwork architecture useful in conjunction with various featuresdescribed herein, wherein the MSO maintains the majority of 5G NR coreinfrastructure.

FIG. 5b is a functional block diagram of a second exemplary MSO/MNOnetwork architecture useful in conjunction with various featuresdescribed herein, wherein the MNO maintains the majority of 5G NR coreinfrastructure.

FIG. 6 is a functional block diagram illustrating a first exemplaryembodiment of an HSS (Home Subscriber Service) and UDM (Unified DataManagement), or HSS+UDM apparatus with PCI conflict resolution support,useful with various embodiments of the present disclosure.

FIG. 7 is a functional block diagram illustrating a first exemplaryembodiment of an enhanced 3GPP-compliant 5G NR gNB apparatus with PCIconflict resolution capability, useful with various embodiments of thepresent disclosure.

FIGS. 3-7 © Copyright 2018-2019 Charter Communications Operating, LLC.All rights reserved. Other Figures © Copyright of their respectivecopyright holders.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.

As used herein, the term “central unit” or “CU” refers withoutlimitation to a centralized logical node within a wireless networkinfrastructure. For example, a CU might be embodied as a 5G/NR gNBCentral Unit (gNB-CU), which is a logical node hosting RRC, SDAP andPDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB thatcontrols the operation of one or more gNB-DUs, and which terminates theF1 interface connected with one or more DUs (e.g., gNB-DUs) definedbelow.

As used herein, the terms “client device” or “user device” or “UE”include, but are not limited to, set-top boxes (e.g., DSTBs), gateways,modems, personal computers (PCs), and minicomputers, whether desktop,laptop, or otherwise, and mobile devices such as handheld computers,PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones,and vehicle infotainment systems or portions thereof.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “distributed unit” or “DU” refers withoutlimitation to a distributed logical node within a wireless networkinfrastructure. For example, a DU might be embodied as a 5G/NR gNBDistributed Unit (gNB-DU), which is a logical node hosting RLC, MAC andPHY layers of the gNB or en-gNB, and its operation is partly controlledby gNB-CU (referenced above). One gNB-DU supports one or multiple cells,yet a given cell is supported by only one gNB-DU. The gNB-DU terminatesthe F1 interface connected with the gNB-CU.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0and 3.1.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices, orprovides other services such as high-speed data delivery and backhaul.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants or Releases of the Long-Term Evolutionwireless communication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), 4G LTE, WiMAX, VoLTE (Voice over LTE),and other wireless data standards.

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3Dmemory, and PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “MNO” or “mobile network operator” refer to acellular, satellite phone, WMAN (e.g., 802.16), or other network serviceprovider having infrastructure required to deliver services includingwithout limitation voice and data over those mediums. The term “MNO” asused herein is further intended to include MVNOs, MNVAs, and MVNEs.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications technologies or networkingprotocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay,3GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, SGNR, WAP, SIP, UDP, FTP,RTP/RTCP, H.323, etc.).

As used herein the terms “5G” and “New Radio (NR)” refer withoutlimitation to apparatus, methods or systems compliant with 3GPP Release15, and any modifications, subsequent Releases, or amendments orsupplements thereto which are directed to New Radio technology, whetherlicensed or unlicensed.

As used herein, the term “QAM” refers to modulation schemes used forsending signals over e.g., cable or other networks. Such modulationscheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM,256-QAM, etc.) depending on details of a network. A QAM may also referto a physical channel modulated according to the schemes.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “Wi-Fi” refers to, without limitation and asapplicable, any of the variants of IEEE Std. 802.11 or related standardsincluding 802.11 a/b/g/n/s/v/ac/ax, 802.11-2012/2013 or 802.11-2016, aswell as Wi-Fi Direct (including inter alia, the “Wi-Fi Peer-to-Peer(P2P) Specification”, incorporated herein by reference in its entirety).

Overview

In one exemplary aspect, the present disclosure provides methods andapparatus for, inter alia, effectively resolving conflicts in PCI valueswhich may exist within two or more mobile networks (e.g., PLMNs) ofrespective different operators when unlicensed spectrum is utilized.

In one implementation, this functionality is provided by specifying oneor more mobility-related parameters associated with various UE, suchthat serving gNBs can determine whether a given UE requires a mobilitycontext, and as such whether it should conduct subsequent RF measurementreporting to report back potential conflicts in PCI it may encounter tothe gNB. In one variant, the measurement reporting is configured tocomply with 5G NR-U required “listen-before-talk” or LBT protocols;i.e., to measure parameters consistent with the LBT protocols as part ofthe detection of any such PCI-based conflicts.

In another variant, a maximum number of PLMNs common to a given PCI isspecified, such that instructed UE(s) will limit themselves tomeasurement reporting on that number of detected PLMNs.

Enhanced PCI confusion resolution capability as described hereinadvantageously allows for UE to utilize unlicensed spectrum (e.g., underthe NR-U model) without complicated network communication andconfiguration requirements between two or more operating networks astypically found in licensed spectrum scenarios.

Moreover, the various aspects of the present disclosure can beimplemented within the existing base of UE with no modification; i.e.,each UE merely uses existing RF measurement reporting functions toprovide the necessary data back to the serving gNB for PCI conflictresolution.

Similarly, only minor modifications to extant network-side architectures(e.g., 3GPP) are needed to support this enhanced functionality.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedwireless access networks (e.g., 5GS and ECS) associated with orsupported at least in part by a managed network of a service provider(e.g., MSO and/or MNO networks), other types of radio accesstechnologies (“RATs”), other types of networks and architectures thatare configured to deliver digital data (e.g., text, images, games,software applications, video and/or audio) may be used consistent withthe present disclosure. Such other networks or architectures may bebroadband, narrowband, or otherwise, the following therefore beingmerely exemplary in nature.

It will also be appreciated that while described generally in thecontext of a network providing unlicensed spectrum service to a customeror consumer or end user or subscriber (i.e., within a prescribed servicearea, venue, or other type of premises), the present disclosure may bereadily adapted to other types of environments including, e.g.,outdoors, commercial/retail, or enterprise domain (e.g., businesses), oreven governmental uses (including e.g., quasi-licensed spectrum such asCBRS). Yet other applications are possible.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Methods

Referring now to FIGS. 3-3C, various embodiments of the methods of,inter alia, cell identification and operating a wireless network, areshown and described in detail. It will be appreciated that while thesemethods are described primarily in the context of a 3GPP-based (i.e.,E-UTRAN and 5G NR) architecture, the various methods are in no way solimited, and may be readily adapted and applied to other types orconfigurations of wireless network such as for instance MulteFire™-basednetworks, such adaptation and application being within the skill levelof the ordinary artisan given the present disclosure.

FIG. 3 shows a first embodiment of the generalized method for cellidentification according to the present disclosure. Per step 302 of themethod 300, one or more candidate UE(s) for PCI confusion resolution areidentified. As described in greater detail below, in one implementation,this identification is accomplished based on a mobility-related factoror determination.

Next, per step 304, the cognizant gNB instructs the identified set ofUEs from step 302 to perform Measurement Reports. As discussed below, inone implementation, the Measurement Reports are conducted taking the LBT(Listen Before Talk) protocol into account.

Lastly, per step 306, the gNB uses data from the Measurement Reportsprovided by the UE(s) to update the current white and/or black lists toinclude/exclude unrelated or improper PCI values.

Referring now to FIG. 3a , one particular implementation of step 302 ofthe method 300 is shown. Specifically, within step 302 of the method300, a mobility-related determination is performed. Specifically, thegNB identifies at least some of the candidate set of UEs as requiring ornot requiring application of the confusion resolution mechanism based onthe presence or absence of a prescribed parameter (in one variant, thevalue “No Mobility Required” or NMR is used, although other values andforms of parameter may be used with equal success. Specifically, forcertain UE(s) such as those used for Fixed Wireless Access (FWA), nomobility scenarios exist and hence such scenarios need not be supported.If a given gNB can identify such UE(s), then it can request theidentified UE(s) to not perform Measurement Reports for certain PCI(s).

In one approach, the presence or absence of this NMR or similarparameter is conducted when such UE(s)/users perform registration withthe 5GC (see 3GPP TS 23.501, and 23.502); i.e., the “No MobilityRequired” value is present in the N2-AP INITIAL CONTEXT SETUP REQUEST(which carries Registration Accept per TS 23.502 Section 4.2.2.2.2, step21); see also TS 38.413 Section 8.3.1.2, step 2, each of the foregoingincorporated herein by reference in its entirety. Specifically, the AMF(Access and Mobility Management Function) may initiate the InitialContext Setup procedure if (i) a UE-associated logical NG-connectionexists for the UE, or (ii) if the AMF has received the RAN UE NGAP ID IEin an INITIAL UE MESSAGE message, or (iii) if the NG-RAN node hasalready initiated a UE-associated logical NG-connection by sending anINITIAL UE MESSAGE message via another NG interface instance. Theprocedure uses UE-associated signalling.

Hence, per step 312 of the method of FIG. 3a , the AMF accesses theUE/subscription data for the relevant UE (e.g., by accessing the globalDB 402 at the HSS+UDM entity 401 discussed below), and inserts thisaccessed data into the relevant context message (e.g., CONTEXT SETUPREQUEST) transmitted to the cognizant gNB (step 314).

To support the presence or absence of this NMR parameter within theabove registration process, in one variant, each UE is characterized attime of generation of the UE(s) and/or users' subscription profilewithin the UDM (Unified Data Management) process or entity, the profiledenoting “No Mobility Required” for that UE/user. For instance, anend-user may be utilizing a fixed 5G-enabled wireless device such as asmart TV, DSTB, gateway, router, IoT-enabled device, etc. which has nomobility capability.

As a brief aside, it will be recognized that as used herein, the term“mobility” refers more to intra-cell mobility, versus inter-cellmobility. Specially, any device is mobile to some degree; i.e., one canset up their smart TV or IoT device within their premises, and thenlater move it to another location within the same premises. However,under such scenarios, from a PCI perspective, the device is immobile.Notwithstanding, the present disclosure also contemplates use of two ormore “grades” or levels of mobility characterization in one alternateembodiment; e.g., (i) No Mobility Required, (ii) Limited MobilityRequired, and (iii) Full Mobility Required. Under such model, the gNBcan apply different protocols to the different levels of mobilitysupport needed; e.g., the method 300 above for NMR, another for LAIR(e.g., a hybridization of the method of FIG. 3 and mobility-enabledapproaches in scenarios where the UE or another gNB signals that it thenrequires mobility in that limited instance), and yet another for FMRscenarios.

It will also be appreciated that while the foregoing approach ofaccessing the UDM (e.g., via the AMF) as part of the Attach procedure(and generating the INITIAL CONTEXT SETUP REQUEST sent to the gNB withmobility-related data) is used to determine UE mobility status forpurposes of PCI management, other approaches may be used consistent withthe present disclosure. For example, in another variant, the UE itselfsupplies the NMR or other parameter, such as via another Attachprocedure or setup message.

As yet another variant, the parameter(s) of interest (e.g., NMR) may beprovided in RRC signaling between the UE and gNB, including in somecases coupling with a subscription-based solution (the latter which isadvantageously reliable and operator-controllable) as described ingreater detail below with respect to Appendix II. Referring again toFIG. 3a , the gNB, upon receiving the context message from the AMF (step316), analyzes the message and extracts the NMR value if present, andstores the NMR value for the duration of the UE's session context (i.e.,during RRC_CONNECTED and RRC_INACTIVE states) per step 318. As describedin greater detail below, the gNB may use the NMR data e.g., whendeciding to request one or more UE(s) to perform Measurement Reporting,and correspondingly update white/black lists for Measurement Reportingif deemed necessary

It will also be recognized that in other variants, the NMR or othermobility-related data may be used as a basis for inclusion as well asexclusion of UEs within the gNB identification logic. For example, if itis desired to identify UE(s) with no mobility requirements, then thosecarrying the NMR parameter (e.g., via the CONTEXT REQUEST from the AMFas described above) are included, and all else are excluded. Conversely,if it is desired to identify only UE(s) having mobility requirements,those carrying the NMR parameter are excluded, and all else included. Itwill be recognized that the “negative” of this approach can be used aswell consistent with the present disclosure; i.e., all UE(s) not withina FWA or no-mobility context can have for instance an “MR” (MobilityRequired) parameter, while all others have no such value. Likewise, inanother variant, those UE(s) requiring mobility may carry the MRparameter, while those under FWA carry the NMR parameter. Since thenumber of FWA-context devices is expected to be much less than themobility-required devices, it is more efficient to merely label theFWA-context devices with NMR or the like in such scenarios. In oneimplementation, UEs not supporting NMR functionality by definition willbe considered normal UEs, although it will be recognized that they mayalso be affirmatively identified or labeled as not supporting parameter(e.g., NMR) functionality.

Referring now to FIG. 3b , one implementation of step 304 of the method300 of FIG. 3 is described. Specifically, per step 320, the cognizantgNB determines at least one “target” PCI, as well as a duration valuespecifying the duration for which the requested measurement is to beperformed (i.e., in order to sufficiently collect required NCGI datafrom all PLMNs broadcasting the same PCI for a given frequency) per step322. As noted, for a given cell, a gNB supports many UEs. Based on thoseUEs' mobility state information already available the gNB (e.g., the NMRparameter), the gNB requests the identified sub-set of UEs to perform(or not perform, depending on the constitution of the sub-set asdiscussed supra) additional Measurement Reports to resolve PCIconfusion. In one such approach, the gNB affirmatively instructs onlythose UE not having the NMR parameter associated to perform theMeasurement Reports. In another approach, the gNB affirmativelyinstructs only those UE having the NMR parameter associated to notperform the Measurement Reports.

As a brief aside, unlicensed spectrum coexistence is a key principle inboth LAA (LTE) and NR-U (5G). This coexistence is accomplished bydynamically selecting available channels within the unlicensed band toavoid e.g., Wi-Fi users. If no available or clear channel is present,channels are shared “fairly” among the users using the Listen BeforeTalk (LBT) protocol. As in LTE-LAA and other technologies, the LBTprotocol in NR-U is a mechanism by which measurements of a given carrierare obtained, and use or “backoff” determined based on the measurements.

Accordingly, in one implementation, step 324 of FIG. 3b includes thefollowing ASN.1 additions to the MeasObjectNR IE (information elementwhich specifies information applicable for SS/PBCH block(s)intra/inter-frequency measurements or CSI-RS intra/inter-frequencymeasurements) to instruct the UE(s) on the requisite scan time(including flexibility to change as needed dynamically)—see Appendix Ihereto:

measReportLBTScanTime INTEGER (XX..maxMeasRepPCIScanTime) OPTIONAL --Time for which the UE scans for all possible SSBs being broadcasted inthe same PCI by different PLMNs maxMeasRepPCIScanTime INTEGER ::= YY(where YY is the Maximum time (in ms) for which a given PCI is scanned)

As a brief aside, in 5G NR, the SSB (the Synchronization Signal/PBCHBlock) consists of synchronization signal (i.e., PSS and SSS) and PBCHchannels. The SSB burst set is re-transmitted every 5 ms, and withinevery SSB burst set the SSB is transmitted at a certain periodicity.Since SSB is unique to a gNB on a per-cell, per-beam basis, it is safeto assume that when the SSB is transmitted continuously over a physicalmedium (e.g., an RF frequency), within a 5 ms period, a UE looking forthe SSB should be able to read it.

In that NR requires tight time synchronization between the gNB and UE,it is also safe to assume that multiple gNBs both within the same PLMNand across different PLMNs are coordinated to an accurate timing source(e.g., atomic clock). Hence, time deviation among the gNBs of differentPLMNs is negligible.

In LTE-LAA, the maximum COT (channel occupancy time) following asuccessful LBT procedure is 10 ms (see TS 37.213 v15.1.0 clause 4.1.1,incorporated herein by reference in its entirety). One implementation ofthe methodology described herein, based on the assumption that an NRsystem uses the same 10 ms value, uses a 15 ms total (5 ms+10 ms) timefor the UE to scan for all possible SSBs being broadcast in the samePCI, such as by different PLMNs. As such, the previously discussed ASN.1additions to the MeasObjectNR IE in such implementations can beconfigured with values of XX and YY of 5 ms and 15 ms, respectively—thatis:

measReportLBTScanTime INTEGER (5..maxMeasRepPCIScanTime) OPTIONAL --Need R maxMeasRepPCIScanTime INTEGER ::= 15

Hence, per step 324 of FIG. 3b , the gNB then provides the identifiedUE(s) from step 302 (FIG. 3) with the determined PCI and scan timevalues as above, which enables the UE to scan the PCI(s) and return thegenerated data as part of the Measurement Report procedure.

Per step 326, the gNB extracts the relevant reporting data for thetarget PCI values from the Measurement Reports of the “instructed” UEafter such Reports have been received (e.g., signal strength data forthe prescribed frequencies).

In another implementation (discussed below with respect to FIG. 3c ),the gNB further instructs the UE(s) to implement a second parameterrelating to a prescribed maximum number of PLMNs to report on.

Referring now to FIG. 3d , one implementation of the method step 306 ofFIG. 3 is now described in detail. As shown, per step 330, the gNBassembles the extracted Measurement Report data from the directed UE(s)relating to all NCGI(s), in response to gNB's PCI to NCGI resolutionrequest. In one variant, this is performed on a per-PCI basis, althoughother schemes may be utilized consistent with the present disclosure.

Per step 332, the gNB logic then evaluates the received data for eachtarget PCI to determine whether conflicts are present. Per steps 334 and336 the gNB can, based on various criteria including the results of theevaluation of step 332, decide to update the current white list and/orblack list; i.e., specifying those PCI on which it wishes tosubsequently obtain Measurement Reports.

Notably, extant white list/black list approaches only allow for theinclusion of PCI values (i.e., in the PCI-Range IE). The PCI-Range IE isdefined in TS 38.331 and is used to encode either a single or a range ofphysical cell identities. Per TS 38.331, the range is encoded by using astart value and by indicating the number of consecutive physical cellidentities (including start) in the range. For fields comprisingmultiple occurrences of PCI-Range, the Network may configure overlappingranges of physical cell identities. The “range” field in the PCI-RangeIE indicates the number of physical cell identities in the range(including start). For example, the value n4 corresponds with 4, n8corresponds with 8. The UE applies a value of 1 in the case the field isabsent, in which case only the physical cell identity value indicated bythe “start” field applies. The “start” field indicates the lowestphysical cell identity in the range.

In the particular case of PCI confusion, however, the extant structureis not sufficient. Specifically, what is required is the ability toeither enable or disable Measurement Reports from PCI(s) of a specificPLMN. Therefore, the following modified ASN.1 PCI-Range IE is providedper one embodiment of the present disclosure to support such additionalspecificity:

Modified PCI-Range Information Element

-- ASN1START -- TAG-PCI-RANGE-START PCI-Range ::= SEQUENCE { startPhysCellId, range  ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64,n84, n96, n128, n168, n252, n504, n1008,spare1} OPTIONAL -- Need SnrCellId  CellGlobalIdNR OPTIONAL -- PCIs of specific PLMNs for whichMeasurements Reports are to be disabled } CellGlobalIdNR ::=  SEQUENCE {plmn-Identity PLMN-Identity, cellIdentity CellIdentity } --TAG-PCI-RANGE-STOP -- ASN1STOP

As referenced above, in another variant, the parameter(s) of interest(e.g., NMR) may be provided in RRC signaling between the UE and gNB,including in some cases coupling with a subscription-based solution (thelatter which is advantageously reliable and operator-controllable). Forexample, in one implementation, the UE provides the parameter(s) (e.g.,NMR) within the UE NR-Capability IE, which is included inUECapabilityInformation message (the latter which is sent in response toUECapabilityInquiry message). As such, relevant portions of TS 38.331may be modified as described below.

Specifically, upon reception of the foregoing data, the cognizant gNBhas an understanding of whether a given UE can support the parametricdetermination (e.g., NMR) or not. Combined with the information receivedover the N2-AP INITIAL CONTEXT SETUP REQUEST as described elsewhereherein, the gNB can accurately decide whether or not to apply NMR forthis UE. In one implementation, within the exemplary UECapabilityInformation IE, the UE-CapabilityRAT-ContainerList is used. The IEUE-CapabilityRAT-ContainerList contains a list of radio accesstechnology specific capability containers. For NR, the IE UENR-Capability IE is used to convey the NR UE Radio Access CapabilityParameters, see TS 38.306. Appendix II hereto illustrates an exemplaryimplementation of the UE NR-Capability IE including added NMR parametersaccording to the present disclosure.

In another embodiment of the methodology (see FIG. 3c ), the gNB mayalso utilize a second parameter to control the behavior of the UEconducting the measurement reporting. This second parameter, asdescribed in greater detail below, may be used in tandem with (or evenin place of in some circumstances) the previously described timingduration parameter(s).

Specifically, it is recognized by the inventors hereof that there is noreliable mechanism for knowing a priori how many PLMN operators will beoperating within a given cell's area at any given point in time. Duringthe initial deployment phase of NR technology, it is expected that thenumber of PLMN operators will be comparatively small and contained;however, as deployment continues over time, this assumption may nolonger hold true. As discussed above, the ability of the gNB to utilizescan time limit(s) which may be applied to the PCI search and reportingis already provided herein. However, it may be the case e.g., that theuse of the time-bounded limit may not be sufficient to adequatelyrestrict the measurement reporting conducted by the UE; i.e., if alarger number of PLMNs are present (e.g., more than 5), they may all bewithin the prescribed scan window, including in some cases being“densely packed” within a smaller portion of the scan window due toe.g., statistical variation, and hence the UE would still be conductinga higher number of scans/reports than desired, even with the scan windowlimit imposed.

As such, an additional mechanism by which the number of PLMNscorresponding to the PCI (and hence reports corresponding theretogenerated by the UE(s)) may be limited is proposed herein; i.e., a“report-bound” in addition to the previously described “time-bound” onthe PLMN search. Specifically, in one implementation, an addition to theASN.1/TS 38.331 MeasObjectNR IE is used as shown below:

maxPLMNsPerPCIToReport INTEGER ::= (1..maxNrOfPLMNsPerPCIToReport)OPTIONAL -- Maximum number of PLMNs for the same PCI for Measurementreports are to be generated by the UE

In one implementation, the constant maxNrOfPLMNsPerPCIToReport isdefined as follows:

-   -   maxNrOfPLMNsPerPCIToReport INTEGER::=20

Appendices III and IV hereto illustrate various embodiments of the useof the above value within the ASN.1 MeasObjectNR IE.

Note also that in Appendix IV, the following elements have been added inplace of the CellGlobalNR IE of the alternate embodiment:

blackCellsToAddModList BlockPCIOfCertainPLMNs blackCellsToRemoveListBlockPCIOfCertainPLMNs

Note also that in Appendix IV, several new elements have been added,including e.g., the following:

BlockPCIOfCertainPLMNs::= SEQUENCE { cellIdentity CellIdentityplmn-Identity PEMN-Identity

Referring again to FIG. 3c , the method proceeds similar to that of FIG.3b described supra; however, at step 323, the further gNB determines themaximum number of PLMNs (e.g., 5 as in the example above) for whichmeasurement reporting is to be conducted by the UE. This determinedvalue may be on a global basis (i.e., all UE), or individual to one ormore UE within the broader population.

Per step 325, the gNB instructs the relevant UE(s) with the target PCIvalue(s), duration(s), and also maximum PLMN number selected per step323.

It will be appreciated that the exemplary specified constant value above(5) may be varied as needed, based on operational or otherconsiderations. This variation may even be dynamic in nature, such ase.g., by logic having insight into the number of active PLMNs as afunction of time (which may be correlated for example to status ofoperational deployment, planned maintenance outages, etc.). The value ofthe constant may also be related to the above-described scan timevalue(s), such as where it is desired to use themaxNrOfPLMNsPerPCIToReport parameter to limit the measurement reportingwhen a longer scan time window is used (i.e., when the window is so longas to effectively provide no limitation).

It will also be appreciated that the scan time parameter(s) and themaximum number of PLMN parameter may be used heterogeneously acrossdifferent UE being served by a common gNB. For instance, it may bedesirable in some cases to have one subset of the UE populationimplement the scan time parameter(s) alone, while others utilize thecombination of scan time and maximum PLMN number parameters. Since RRCparameters are UE-specific, different UEs can be provided differentvalues by the gNB given its knowledge of the topology, statistics,operational considerations, etc. These heterogeneous uses may also becombined with the conjunctive/selective use of the scan time and maximumPLMN numbers described herein to optimize the network on aper-UE/per-gNB basis. For example, even two UE's within the same subsetmay have differing combinations/constant values, such as in the casewhere Combination A (scan time parameter=R, maximum PLMN number=S) isapplied to a portion of the second subset mentioned above (combinationsubset), while Combination B (scan time parameter=T, maximum PLMNnumber=U) is applied to another portion of that same second subset.

Further, as referenced above, the present disclosure contemplates use ofindividual ones of the parameters (e.g., scan time/maximum number ofPLMNs) either individually or in combination, depending on factors suchas operational circumstance. It will be appreciated that such differentparameters may have respective different benefits/optimizations, therebymaking their use non-identical. For instance, one risk or potentialdetriment of using the scan time parameter alone is that the cognizantgNB may not get an accurate representation of all possible combinationsof PLMNs which a given UE is experiencing. This disability can beresolved by, for instance, the gNB performing cell scans itself, orperforming ANR, but, neither of these “work arounds” is optimal.

Conversely, one risk or potential detriment in using the maximum PLMNnumber parameter alone is that as the number of PLMNs for a given PCIincreases, the affected UE(s) will spend progressively longer times (andresources) scanning for all possible PLMNs (i.e., until the maximumspecified number is reached).

Accordingly, in one exemplary implementation of the disclosure, aconjunction of both parameters may provide an optimal balance of UEpower consumption obtaining the most accurate data regarding the UE'senvironment. It will be recognized, however, that such uses may beselectively invoked or adjusted; for instance, where UE electrical powerconsumption is low (e.g., where the battery charge is significantlydepleted or below a prescribed threshold), this information may be usedto “rebalance” the optimization, such as by e.g., reducing the maximinnumber of PLMNs specified in the constant maxNrOfPLMNsPerPCIToReport.

In yet another embodiment of the disclosure, rather than use of CGIreporting—e.g., cgi-Info IE in MeasResultNR (which may or may not beactive based on circumstance; i.e., is optional, and CGI reporting maynot be turned on), the PLMN-ID is reported when performing RSRQ/RSRP orother signal strength indicator (SSI) measurements, based on PCIreporting.

Specifically, as shown in the embodiment of Appendix III, the PLMN-IDmay be added to MeasResultNR, so that the PLMN-ID can be obtained incases where CGI reporting is not invoked. Alternatively, it can beobtained from the CGI-nfo IE where utilized.

Network Architecture—

FIG. 4 shows one embodiment of a 5G NR-based architecture 400, includingaspects as defined in 3GPP TS 23.501, according to the presentdisclosure. Specifically, as shown, the architecture 400 includes aUDM-based data repository or database 402 of UE characterizing data(such as for instance the NMR and/or other parameters previouslydescribed) to be used consistent with the methods of FIGS. 3-3C. Thearchitecture also includes a PCI Conflict Resolution Entity (PCRE) 404,as well as a local characterizing database 406 for all or a subset ofthe gNBs (within the NG-RAN). For example, in one scenario, all RAN (andtheir gNBs) include a PCRE 404 and database 406. In another scenario,only gNBs supporting particular unlicensed spectrum functionalityinclude the PCRE/database. In yet another scenario, gNBs expected tohave significant PCI conflicts (e.g., by virtue of having a largeunlicensed footprint or presence nearby or overlapping within the RANcoverage area) include the PCRE/database. It will be appreciated thatany number of deployment configurations and scenarios may be utilizedconsistent with the present disclosure, the architecture 400 of FIG. 4being merely exemplary.

FIG. 4a is a functional block diagram of a first exemplary embodiment ofan enhanced E-UTRAN/5G network architecture according to the presentdisclosure. Specifically, as shown in FIG. 4a , the architecture 400includes generally both a legacy or 4G/4.5G RAN 422 and a 5G-NR RAN(NG-RAN) 424, although it will be appreciated that configurations withdifferent numbers of and/or other types of RANs may be utilizedconsistent with the present disclosure; e.g., a given PLMN may havemultiple RANs including mixtures of legacy and next-generationtechnology, as well as unlicensed (e.g., ISM-band) and/or quasi-licensed(e.g., CBRS) apparatus and a capability associated therewith. In theillustrated embodiment, the PLMN represented within the diagram is thehome PLMN (HPLMN) of the 5G NR-U enabled UE.

As shown, the 5G RAN 424 of the type described subsequently herein indetail is configured to include both a local parameter (e.g., NMR inthis example) database 406, and PCRE 404. In this embodiment, thePCRE/NMR database are located within the 5G NR CU (central unit) of therelevant gNBs (not shown), although it will be appreciated that thesecomponents may be located in different locations, whether individuallyor collectively.

Also shown is the global NMR database 402, here logically disposedwithin the HSS+UDM functionality of the 5GC. The N8 interface as shownenables communication between the UDM process (and hence the global DB402) and the serving AMF 426 in support of the PCI confusion resolutionfunctions described herein.

In the architecture 440 of FIG. 4b , the PCRE 404 and local NMR database406 are disposed logically within the AMF function 446, and hencemultiple CU/DU (gNBs) can be provided with the PCI conflict resolutionfunction more centrally as opposed to the configuration of FIG. 4a . Inorder for each gNB to receive and process the NMR data, a client orlocal portion of the PCRE (PCRE_(cl)) 442 and server portion (PCRE_(s))444 are used, with the PCRE_(s) performing the evaluation anddetermination logic of e.g., FIGS. 3-3 c, and the PCRE_(cl) merelyacting as an “implementation minion” process to in effect configurevarious UE with which it is in contact for Measurement Reporting (or nosuch reporting) as required.

In the architecture 460 of FIG. 4c , the PCRE_(s) 444 is disposed withinHSS+UDM of the UE's home PLMN, while the client (PCRE_(cl)) 442 isdisposed within the visited PLMN (i.e., within the CU/DU of the NG-RANgNB(s)). The local NMR DB 406 is obviated in favor of a single global DB402 at the HSS+UDM.

As discussed with respect to FIGS. 5a and 5b below, depending on thedivision of ownership/operational responsibility between the NR(licensed) and NR-U (unlicensed) infrastructure, various combinations ofcomponent placement and configuration are possible in supporting the PCIconflict resolution functionality. For instance, in one variant, an MSO(e.g., cable or satellite network operator) may maintain NG-RANfunctionality within their service domain (such as via their owndeployed “standalone” or SA 5G NR-U enabled gNBs, as well as otherunlicensed and/or quasi-licensed devices such as Wi-Fi APs, CBRS CBSDs,etc., with which the NR-U functionality must co-exist. Alternatively, inanother variant, the MNO (e.g., cellular service provider) may maintainall infrastructure (including the PCI conflict resolution enabled gNBsand the various NMR databases), and merely lease or otherwise enablecustomers of the MSO to access the MNO infrastructure.

As such, the placement and configuration of the various PCI conflictresolution processes (i.e., PCREs, NMR databases, etc.) is envisioned tovary accordingly. Advantageously, since standardized 5G NR protocols andinterfaces are utilized, communication between the various entities isstraightforward (i.e., as opposed to proprietary protocols utilized ineach domain).

Service Provider Network—

FIG. 5a illustrates a typical service provider network configurationuseful with the features of the enhanced PCI conflict resolutionapparatus and methods described herein, including the enhanced 3GPParchitectures of FIGS. 4-4 c. This service provider network 500 is usedin one embodiment of the disclosure to provide backbone and backhaulfrom the service provider's service nodes, such as HFC cable orFTTC/FTTH drops to different premises or venues/residences. For example,one or more stand-alone or embedded DOCSIS cable modems (CMs) 512 are indata communication with the various NR (5G) architecture components(e.g., DU's and CU's) so as to provide two-way data communication to theserved components.

Also provided within the architecture 500 of FIG. 5 is an MSO interface532 to one or more MNO networks 511, such as those of an MVNO. Theexemplary MNO/MVNO infrastructure or domain includes a number of 3GPPgNBs 544 a-b and eNBs as shown, thereby providing 3GPP 4G/4.5G/5Gcoverage to authorized users of the MNO/MNVO network. These components(and others needed to support the E-UTRAN and 5G RAN in the architectureof e.g., FIG. 4a , such as the SGW and MME/MME_(e)—not shown in FIG. 5)interface with the MSO-domain (and ultimately the HSS+UDM with globalNMR DB) via e.g., a data interface 550 to the MSO backbone 531. In oneembodiment, this interface 532 supports the S5/S8/S6a 3GPP interfacesbetween the S-GW and P-GW (S8 is used when roaming between differentoperators, while S5 is network-internal).

The UE may include two radio transceivers (one for 3GPP LTE, and one for3GPP NR including NR-U), or alternatively a common unified dual-modetransceiver, as well as protocol stacks serving the respectivetransceivers for functions including support of higher layer processessuch as authentication.

Also included in the infrastructure 500 of FIG. 5a are the HSS+UDM withglobal NMR DB 402, PGW, h-PCF/h-PCRF, AMF 426, v-PCF, v-SMF, and UPFentities of FIGS. 4-4 c. While these entities are shown as part of theMSO “core” infrastructure portion in this embodiment, it will beappreciated as previously discussed that such entities each (i) may bedistributed at two or more different/other locations within the MSO coreor service domain(s); (ii) may be combined with each other or with otherMSO infrastructure components (including those at the service domain),and (iii) may be virtualized as software/firmware processes within othercomponents (such as MSO system servers, RAN infrastructure, etc.).Hence, the illustrated configuration of FIG. 5a is merely illustrativein this regard.

Moreover, it will be recognized that while the architecture 500 of FIG.5a is characterized in the context of the embodiment of FIG. 4a (i.e.,with the PCRE functionality logically and functionally contained withinthe gNBs of the MSO service domain, the architecture 500 may readily beadapted by those of ordinary skill given the present disclosure forother embodiments, including for example those of FIGS. 4b and 4 c.

In certain embodiments, the service provider network architecture 500also advantageously permits the aggregation and/or analysis ofsubscriber- or account-specific data (including inter alia, particularCU or DU or E-UTRAN eNB/femtocell devices associated with suchsubscriber or accounts, as well as their mobility or FWA status aspreviously discussed) as part of the provision of services to usersunder the exemplary delivery models described herein. As but oneexample, device-specific IDs (e.g., gNB ID, Global gNB Identifier, NCGI,MAC address or the like) can be cross-correlated to MSO subscriber datamaintained at e.g., the network head end(s) 507, or within the HSS+UDM(and associated global NMR database 402) where maintained by the MNO, soas to permit or at least facilitate, among other things, PCI conflictresolution and Measurement Report configuration.

As a brief aside, a number of additional identifiers over and above thePCI discussed supra are used in the NG-RAN architecture, including thoseof UE's and for other network entities. Specifically:

-   -   the AMF Identifier (AMF ID) is used to identify an AMF (Access        and Mobility Management Function 426 shown in FIGS. 4-4 c);    -   the NR Cell Global Identifier (NCGI), is used to identify NR        cells globally, and is constructed from the PLMN identity to        which the cell belongs, and the NR Cell Identity (NCI) of the        cell;    -   the gNB Identifier (gNB ID) is used to identify gNBs within a        PLMN, and is contained within the NCI of its cells;    -   the Global gNB ID, which is used to identify gNBs globally, and        is constructed from the PLMN identity to which the gNB belongs,        and the gNB ID;    -   the Tracking Area identity (TAI), which is used to identify        tracking areas, and is constructed from the PLMN identity to        which the tracking area belongs, and the TAC (Tracking Area        Code) of the Tracking Area; and    -   the Single Network Slice Selection Assistance information        (S-NSSAI), which is used to identify a network slice.

Hence, depending on what data is useful to the MSO or its customers,various portions of the foregoing can be associated and stored toparticular gNB “clients” or their components being backhauled by the MSOnetwork.

The MSO network architecture 500 of FIG. 5a is particularly useful forthe delivery of packetized content (e.g., encoded digital contentcarried within a packet or frame structure or protocol, such as video,audio, or voice data) consistent with the various aspects of the presentdisclosure. In addition to on-demand and broadcast content (e.g., livevideo programming), the system of FIG. 5 may deliver Internet data andOTT (over-the-top) services to the end users (including those of theDU's 506 a-c) via the Internet protocol (IP) and TCP (i.e., over the 5Gradio bearer), although other protocols and transport mechanisms of thetype well known in the digital communication art may be substituted.

The network architecture 500 of FIG. 5a generally includes one or moreheadends 507 in communication with at least one hub 517 via an opticalring 537. The distribution hub 517 is able to provide content to various“client” devices 509 a, 506 a-c, and gateway devices 560 as applicable,via an interposed network infrastructure 545. It will be appreciatedfrom examination of FIG. 5a that the various gNB components (includingthe NR DU's and CU's and their constituent UE_(e)'s) may each act as a“client” device of the network. For example, in many installations, theCU 504 of a given gNB is physically disparate or removed from thelocations of its constituent DU's 506, and hence an interposed (e.g.,wired, wireless, optical) PHY bearer is needed to communicate databetween the DU's and CU of a given gNB. In one such architecture, the CUmay be placed further toward the core of the MSO distribution network,while the various constituent DU's are placed at the edge.Alternatively, both devices may be near the edge (and e.g., served byedge QAMs or RF carriers 540 as shown in FIG. 5a ). In both cases, theMSO infrastructure may be used to “backhaul” data from each device andcommunicate it to, via the MSO infrastructure, the other components,much as two geographically disparate customers of a given MSO mightcommunicate data via their respective DOCSIS modems in their premises.Each component has an IP address within the network, and as such can beaccessed (subject to the limitations of the architecture) by the othercomponents.

Alternatively, the CU's (which in effect aggregate the traffic from thevarious constituent DU's towards the NG Core), may have a dedicated highbandwidth “drop.”

Moreover, a given CU and DU may be co-located as desired, as shown bythe combined units 504 b and 504 c, and 506 b and 506 c in FIG. 5a .This may also be “hybridized,” such as where one constituent DU isco-located (and potentially physically integrated) with the CU, whilethe remaining DU of that CU are geographically and physicallydistributed.

In the MSO network 500 of FIG. 5a , various content sources 503, 503 aare used to provide content to content servers 504, 505 and originservers 521. For example, content may be received from a local,regional, or network content library as discussed in co-owned U.S. Pat.No. 8,997,136 entitled “APPARATUS AND METHODS FOR PACKETIZED CONTENTDELIVERY OVER A BANDWIDTH-EFFICIENT NETWORK”, which is incorporatedherein by reference in its entirety. Alternatively, content may bereceived from linear analog or digital feeds, as well as third partycontent sources. Internet content sources 503 a (such as e.g., a webserver) provide Internet content to a packetized content originserver(s) 521. Other IP content may also be received at the originserver(s) 521, such as voice over IP (VoIP) and/or IPTV content. Contentmay also be received from subscriber and non-subscriber devices (e.g., aPC or smartphone-originated user made video).

The network architecture 500 of FIG. 5a may further include a legacymultiplexer/encrypter/modulator (MEM; not shown). In the presentcontext, the content server 504 and packetized content server 521 may becoupled via a LAN to a headend switching device 522 such as an 802.3zGigabit Ethernet (or “10G”) device. For downstream delivery via the MSOinfrastructure (i.e., QAMs), video and audio content is multiplexed atthe headend 507 and transmitted to the edge switch device 538 (which mayalso comprise an 802.3z Gigabit Ethernet device) via the optical ring537.

In one implementation, the CMs 512 shown in FIG. 5a each service apremises or venue, such as a conference center or hospitality structure(e.g., hotel), which includes one or more DU nodes for provision of 5GNR services, and may also service WLAN (e.g., 802.11-2016 compliantWi-Fi) nodes for WLAN access (e.g., within 2.4 GHz ISM band), or evenE-UTRAN femtocells, CBRS (Citizens Broadband Radio Service) nodes, orother such devices.

In parallel with (or in place of) the foregoing delivery mechanisms, theMSO backbone 531 and other network components can be used to deliverpacketized content to the “client” gNB devices 504, 506 via non-MSOnetworks. For example, so-called “OTT” content (whether tightly coupledor otherwise) can be ingested, stored within the MSO's networkinfrastructure, and delivered to the gNB CU 504 via an interposedservice provider network (which may include a public Internet) 511(e.g., at a local coffee shop, via a DU connected to the coffee shop'sservice provider via a modem, with the user's IP-enabled end-user deviceutilizing an Internet browser or MSO/third-party app to stream contentaccording to an HTTP-based approach over the MSO backbone 531 to thethird party network to the service provider modem (or opticaldemodulator) to the DU, and to the user device via the DU NR wirelessinterface.

It will further be recognized that user-plane data/traffic may also berouted and delivered apart from the CU. In one implementation (describedabove), the CU hosts both the RRC (control-plane) and PDCP (user-plane);however, as but one alternate embodiment, a so-called “dis-aggregated”CU may be utilized, wherein a CU-CP entity (i.e., CU—control plane)hosts only the RRC related functions, and a CU-UP (CU—user plane) whichis configured to host only PDCP/SDAP (user-plane) functions. The CU-CPand CU-UP entities can, in one variant, interface data and inter-processcommunications via an E1 data interface, although other approaches maybe used.

In certain embodiments, each DU 506 is located within and/or servicesone or more areas within one or more venues or residences (e.g., abuilding, room, or plaza for commercial, corporate, academic purposes,and/or any other space suitable for wireless access). Each DU isconfigured to provide wireless network coverage within its coverage orconnectivity range for its RAT (e.g., 5G NR). For example, a venue mayhave a wireless NR modem (DU) installed within the entrance thereof forprospective customers to connect to, including those in the parking lotvia inter alia, their NR or LTE-enabled vehicles or personal devices ofoperators thereof. Notably, different classes of DU 506 may be utilized.In practical terms, some devices may have a working range on the orderof hundreds of feet, while other devices may operate out to thousands offeet or more, the propagation and working range dictated by a number offactors, including the presence of RF or other interferers, physicaltopology of the venue/area, energy detection or sensitivity of thereceiver, etc. Similarly, different types of NR-enabled DU 506 can beused depending on these factors, whether alone or with other wirelessPHYs such as LTE, WLAN, etc.

It will also be appreciated that while described primarily with respectto a unitary gNB-CU entity or device 504 as shown in FIG. 5, the presentdisclosure is in no way limited to such architectures. For example, thetechniques described herein may be implemented as part of a distributedor dis-aggregated or distributed CU entity (e.g., one wherein the userplane and control plane functions of the CU are dis-aggregated ordistributed across two or more entities such as a CU-C (control) andCU-U (user)), and/or other functional divisions are employed.

For instance, the individual DU's 506 in FIGS. 5a and 5b communicatedata and messaging with the CU 504 via interposed physical communicationinterfaces and logical interfaces which may include a user plane andcontrol plane, and be embodied in prescribed protocols such as F1AP. Inone embodiment, one CU 504 is associated with one or more DU's 506, yeta given DU is only associated with a single CU. Likewise, the single CU504 can be communicative with a single NG Core such as that operated byan MNO or MSO. Each NG Core may have multiple gNBs associated therewith.

Two or more gNBs may also be communicative with one another via e.g., anXn interface, and accordingly can conduct at least CU to CU datatransfer and communication. Separate NG Cores may be used for controland user plane (and other) functions of the network. Alternatively, theseparate NG Cores may be logically “cross-connected” to the gNBs of oneor more other NG Cores, such that one core can utilize/control theinfrastructure of another, and vice versa. This may be in “daisy chain”fashion (i.e., one gNB is communicative one other NG Core other than itsown, and that NG Core is communicate with yet one additional gNB otherthan its own, and so forth), or the gNBs and NG Cores may form a “mesh”topology where multiple Cores are in communication with multiple gNBs ormultiple different entities (e.g., service providers). Yet othertopologies will be recognized by those of ordinary skill given thepresent disclosure. This cross-connection approach advantageously allowsfor, inter alia, sharing of infrastructure between two MNOs/MSOs, whichis especially useful in e.g., dense deployment environments which maynot be able to support multiple sets of RAN infrastructure.

It is also noted that heterogeneous architectures of eNBs, Home eNBs orfemtocells (i.e., E-UTRAN LTE/LTE-A Node B's or base stations) and gNBsmay be utilized consistent with the architectures of FIGS. 4-5 a. Forinstance, a given DU may act (i) solely as a DU (i.e., 5G NR-U PHY node)and operate outside of an E-UTRAN macrocell, or (ii) be physicallyco-located with an eNB or femtocell and provide NR coverage within aportion of the eNB macrocell coverage area, or (iii) be physicallynon-colocated with the eNB or femtocell, but still provide NR coveragewithin the macrocell coverage area.

Moreover, the DU/CU architectures set forth in co-owned and co-pendingU.S. patent application Ser. No. 15/945,657 filed Apr. 4, 2018 andentitled “APPARATUS AND METHODS FOR CELL ACTIVATION IN WIRELESSNETWORKS,” incorporated herein by reference in its entirety, may be usedconsistent with the various aspects of the present disclosure.

FIG. 5b is a functional block diagram of a second exemplary MSO/MNOnetwork architecture 550, wherein the MNO maintains the majority of 5GNR core infrastructure, such as within the MNO core portion 552, whichcontains the 5G NR core components outside of the NG-RAN(s), the latterwithin the MSO service domain 554.

HSS+UDM Apparatus—

FIG. 6 illustrates an exemplary configuration of an enhanced HSS+UDM 430according to the present disclosure. As shown, the HSS+UDM 401 includes,inter alia, a processor apparatus or subsystem 602, a program memorymodule 604, mass storage 605 incorporating the parameter (e.g., NMR)database 402 for served UE, HSS (Home Subscriber Server) and UDM(Unified Data Management) logic 606 including management of theforegoing database 402, one or more network interfaces 608.

In the exemplary embodiment, the processor 602 of the HSS+UDM 401 mayinclude one or more of a digital signal processor, microprocessor,field-programmable gate array, or plurality of processing componentsmounted on one or more substrates. The processor 602 may also comprisean internal cache memory, and is in communication with a memorysubsystem 604, which can comprise, e.g., SRAM, flash and/or SDRAMcomponents. The memory subsystem may implement one or more of DMA typehardware, so as to facilitate data accesses as is well known in the art.The memory subsystem of the exemplary embodiment containscomputer-executable instructions which are executable by the processor602.

The processing apparatus 602 is configured to execute at least onecomputer program stored in memory 604 (e.g., a non-transitory computerreadable storage medium); in the illustrated embodiment, such programsinclude HSS+UDM-based NMR DB controller logic 606, such as to serve datafrom requesting AMF or other entities relating to individual UE orsubscriber accounts relating to characterizing data such as NMR data(see discussion of FIGS. 3-3 c above), and other logical functionsperformed by the HSS+UDM as described elsewhere herein. Otherembodiments may implement such functionality within dedicated hardware,logic, and/or specialized co-processors (not shown). The HSS+UDM DBcontroller logic 606 is a firmware or software module that, inter alia,communicates with a corresponding AMF (i.e., for setup for a given UErequesting access via a served NG-RAN with NR-U capability), and/orother upstream or backend entities such as those within the NG Core insome embodiments.

In some embodiments, the HSS+UDM logic 606 utilizes memory 604 or otherstorage 605 configured to temporarily hold a number of data relating tothe various UE's (including UDM registration data, NMR data, etc.) forthe various functions described herein including UE authentication andregistration, PCI conflict resolution, etc.).

The HSS+UDM 401 may further be configured to directly or indirectlycommunicate with one or more authentication, authorization, andaccounting (AAA) servers of the network, such as via the interface 608shown in FIG. 6 and the MSO backhaul (e.g., where the HSS+UDM isdisposed within the MSO infrastructure). The AAA servers, whetherlocally maintained by the MSO or remotely by e.g., an MNO of thesubscriber, are configured to provide services for, e.g., authorizationand/or control of network subscribers (including roaming MNO “visitors”to the MSO RAN(s), and/or roaming MSO subscribers visiting an SPLMN ofan MNO) for controlling access and enforcing policies, auditing usage,and providing the information necessary to bill for services. As such,the AAA servers themselves may be used to supply NMR data or othersimilar context-related data necessary to support PCI conflictresolution according to the present disclosure.

In one exemplary embodiment, the HSS+UDM 401 is maintained by the MSO(see FIG. 5a ) and is configured to utilize a non-public IP addresswithin an IMS/Private Management Network “DMZ” of the MSO network. As abrief aside, so-called DMZs (demilitarized zones) within a network arephysical or logical sub-networks that separate an internal LAN, WAN,PAN, or other such network from other untrusted networks, usually theInternet. External-facing servers, resources and services are disposedwithin the DMZ so they are accessible from the Internet, but the rest ofthe internal MSO infrastructure remains unreachable or partitioned. Thisprovides an additional layer of security to the internal infrastructure,as it restricts the ability of surreptitious entities or processes todirectly access internal MSO servers and data via the untrusted network,such as via a MME or AMF “spoof” or MITM attack whereby an attackermight attempt to hijack one or more functional entities to obtain datafrom the corresponding HSS+UDM.

gNB Apparatus—

FIG. 7 illustrates a block diagram of an exemplary embodiment of a NR-Uenabled gNB apparatus, useful for operation in accordance with thepresent disclosure. In one exemplary embodiment as shown, the gNB (whichmay for instance take any of the forms shown in FIGS. 5a and 5b ,including integrated CU 504 and DU 506, distributed CU/DU, etc.)includes, inter alia, a processor apparatus or subsystem 702, a programmemory module 704, PCRE logic 706 (here implemented as software orfirmware operative to execute on the processor 702), and wirelessinterfaces 710, 720 for communications with the relevant UE's (e.g.,4G/4.5G E-UTRAN and 5G-NR RAN, respectively).

The 5G RF interface 720 may be configured to comply with the relevantPHY and CU DU functional “splits” (e.g., Options 1 through 8) accordingto the relevant 3GPP NR standards which it supports. Returning again toFIG. 7, the antenna(s) 715, 725 of the radios of the gNB(s) may includemultiple spatially diverse individual elements in e.g., a MIMO- orMISO-type configuration, such that spatial diversity of the receivedsignals can be utilized. Moreover, a phased array or similar arrangementcan be used for spatial resolution within the environment, such as basedon time delays associated with signals received by respective elements.

In one embodiment, the processor apparatus 702 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, or plurality of processing components mounted on one or moresubstrates. The processor apparatus 702 may also comprise an internalcache memory. The processing subsystem is in communication with aprogram memory module or subsystem 704, where the latter may includememory which may comprise, e.g., SRAM, flash and/or SDRAM components.The memory module 704 may implement one or more of direct memory access(DMA) type hardware, so as to facilitate data accesses as is well knownin the art. The memory module of the exemplary embodiment contains oneor more computer-executable instructions that are executable by theprocessor apparatus 702. A mass storage device (e.g., HDD or SSD, orNAND/NOR flash or the like) is also provided as shown.

The processor apparatus 702 is configured to execute at least onecomputer program stored in memory 704 (e.g., the logic of the PCREincluding enhanced functions of PCI conflict resolution and operationaccording to the methods of FIGS. 3-3 c herein, in the form of softwareor firmware that implements the various functions). Other embodimentsmay implement such functionality within dedicated hardware, logic,and/or specialized co-processors (not shown).

In some embodiments, the PCRE logic 706 also utilizes memory 704 orother storage 705 configured to temporarily and/or locally hold a numberof data relating to the various NMR data and associations for thevarious UE which it services under the NR-U standard(s). In otherembodiments, application program interfaces (APIs) may also reside inthe internal cache or other memory 704. Such APIs may include commonnetwork protocols or programming languages configured to enablecommunication between the PCRE and other network entities (e.g., via API“calls” to or from the HSS+UDM 401 or AMF 426).

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

What is claimed is:
 1. A computerized user device, comprising: a digitalprocessor apparatus; a wireless network interface apparatus configuredfor data communication with the digital processor apparatus and aplurality of wireless-enabled data networks; and at least one storagedevice in data communication with the digital processor apparatus, theat least one storage device comprising at least one computer programhaving a plurality of instructions configured to, when executed by thedigital processor apparatus, cause the computerized user device to:insert parametric data relating to a use scenario or context into aprotocol message for transmission to a base station, the parametric dataconfigured to be extracted by the base station to enable determinationof whether measurement reporting should be performed for at least oneother computerized user device; and responsive to a determination thatmeasurement reporting should be performed, perform the measurementreporting with respect to (i) a first identifier associated with atleast a target wireless-enabled data network and (ii) one or more secondidentifiers associated with at least a portion of the plurality ofwireless-enabled data networks, the first identifier in conjunction withthe one or more second identifiers enabling unique identification of thetarget wireless-enabled data network.
 2. The computerized user device ofclaim 1, wherein the at least one computer program is further configuredto, when executed, cause the computerized user device to providemobility-related parametric data indicative that no mobility is requiredvia a capabilities information element (IE), the mobility-relatedparametric data configured to enable a receiving base station todetermine whether the user device can support a PCI (Physical CellID)-based conflict resolution mechanism or not and, based at leastthereon, (ii) decide whether or not to apply the PCI (Physical CellID)-based conflict resolution protocol.
 3. The computerized user deviceof claim 1, wherein the user device comprises a 3GPP 5G NR (New Radio)compliant user equipment (UE).
 4. The computerized user device of claim1, wherein the plurality of instructions are further configured to, whenexecuted, cause the computerized user device to select a duration forwhich the measurement reporting is to be performed, and perform themeasurement reporting over the duration with respect to the firstidentifier, the selected duration enabling collection of datacorresponding to the one or more second identifiers.
 5. The computerizeduser device of claim 1, wherein the parametric data relating to the usescenario or context comprises data indicative of whether mobility of theat least one other computerized user device is required or not.
 6. Thecomputerized user device of claim 5, wherein the plurality ofinstructions are further configured to, when executed by the digitalprocessor apparatus, cause the computerized user device to, responsiveto a determination that measurement reporting should not be performed,exclude the at least one other computerized user device from a conflictresolution mechanism relating to the first identifier and the respectivesecond identifiers.
 7. A method for cell identification within awireless network, the method comprising: accessing a database ofmobility-related parameters associated with each of a plurality of userdevices either (i) at time of initial user device account registration,or (ii) based on a user input via a respective one of the set of userdevices thereafter; identifying a set of user devices to which to applya cell identifier resolution mechanism, the identifying based at leaston (i) the accessing of the database, and (ii) a respectivemobility-related parameter associated with each of the set of userdevices; instructing at least a portion of the identified set of userdevices to perform a measurement protocol; and based on the results ofthe measurement protocol, configure at least one listing of cellidentifiers.
 8. The method of claim 7, wherein the user devices comprise3GPP (Third Generation Partnership Project) compliant user equipment(UEs), and the cell identifiers comprise PCI (Physical Cell ID) values.9. The method of claim 7, wherein the identifying the set of userdevices for which to apply the cell identifier resolution mechanismcomprises identifying the set of user devices based at least on therespective mobility-related parameter associated with each of the set ofuser devices, the respective mobility-related parameter provided by atleast each of the respective user devices of the set pursuant toregistration with a 3GPP (Third Generation Partnership Project) 5GC(Fifth Generation Core).
 10. The method of claim 9, further comprisingstoring, via at least one gNB (gNodeB) wireless access node, theprovided respective mobility-related parameter for each of the set ofuser devices for at least a duration of each respective user device'ssession context.
 11. The method of claim 10, wherein the storing for atleast the duration of each respective user device's session contextcomprises storing at least during the respective user device'sRRC_CONNECTED and RRC_INACTIVE states.
 12. The method of claim 7,wherein the instructing at least the portion of the identified set ofuser devices to perform the measurement protocol comprises instructingonly those user devices within the identified set not being used forFixed Wireless Access (FWA) to perform the measurement protocol.
 13. Themethod of claim 12, wherein the instructing only those user deviceswithin the identified set not being used for Fixed Wireless Access (FWA)to perform the measurement protocol comprises instructing only thoseuser devices within the identified set not being used for Fixed WirelessAccess (FWA) to perform the measurement protocol only for certainselected one or more PCI (Physical Cell ID) values.
 14. The method ofclaim 7, wherein: the respective mobility-related parameter comprisesdata indicative that no intra-cell mobility nor inter-cell mobility isrequired for a respective one of the set of user devices; andidentifying of the set of user devices to which to apply the cellidentifier resolution mechanism is based at least on an absence of theparameter value associated with the at least portion of the set of theuser devices.
 15. The method of claim 14, further comprising preventingat least a second portion of the identified set of user devices fromperforming the measurement protocol, the preventing based at least on apresence of the parameter value associated with the at least secondportion of the identified set of the user devices.
 16. The method ofclaim 7, wherein: the respective mobility-related parameter comprises aparameter value indicative of that intra-cell mobility or inter-cellmobility is required; and identifying of the set of user devices towhich to apply the cell identifier resolution mechanism is based atleast on a presence of the parameter value associated with the at leastportion of the set of the user devices.
 17. A method of operating awireless network having a plurality of cells, the method comprising:identifying, via at least one of a 3GPP (Third Generation PartnershipProject) —compliant gNB (gNodeB) or a 3GPP-compliant AMF (AccessManagement Function), a subset of a plurality of user devices for whicha prescribed operational configuration or scenario applies; applying,via at least one of the 3GPP-compliant gNB or the 3GPP-compliant AMF, acell identifier resolution mechanism to only others of the plurality ofuser devices and not those of the subset; instructing, via at least oneof the 3GPP-compliant gNB or the 3GPP-compliant AMF, the others of theplurality of user devices to perform a measurement protocol pursuant tothe resolution mechanism; and based on one or more results of themeasurement protocol, configuring, via at least one of the3GPP-compliant gNB or the 3GPP-compliant AMF, at least one of aplurality of cell identifiers.
 18. The method of claim 17, furthercomprising obtaining one or more Public Land Mobile Network ID (PLMN ID)values via a PLMN-ID value within a measurement results reportinginformation element (IE).
 19. The method of claim 17, wherein thecertain operational configuration or scenario comprises a Fixed WirelessAccess (FWA) scenario in which a given user device of the subset isconfigured to not utilize intra-cell mobility or inter-cell mobility.20. The method of claim 17, wherein: the identifying of the subset ofthe plurality of user devices for which the prescribed operationalconfiguration or scenario applies comprises determining an absence or apresence of a prescribed parameter value for each of the plurality ofthe user devices; the subset of the plurality of user devices isassociated with the presence of the prescribed parameter; and the othersof the plurality of user devices are associated with the absence of theprescribed parameter.
 21. The method of claim 17, further comprisingselecting a duration for the performance of the measurement protocolpursuant to the resolution mechanism, the selected duration allowingcollection of data representative of one or more global identifiers fromone or more wireless networks broadcasting a same Physical Cell ID (PCI)value for a given frequency, the PCI value in conjunction with one ofthe one or more global identifiers enabling unique identification of acell within the one or more wireless networks via at least the at leastone listing of cell identifiers.